DRAKHYSYS WORKBENCH V4.8.8 — SELECTED EXIT, OWN ENTRANCE

This fixes the exact V4.8.7 screenshot workflow: changing the main outgoing
exit used to leave the entrance tool attached to the previous incoming exit.
Placing the second point moved the first one.

YOUR WORKFLOW
1. Select an exit under Exits in this source area, or use NEW EXIT and finish
   its polygon with FINISH / UPDATE EXIT.
2. Click PLACE / MOVE ENTRANCE IN MAP, then click its point on this map.
3. Click ADD / UPDATE ENTRANCE.
4. Select/create another exit and repeat. Both points stay saved.
5. Select the first exit again to see and update its own entrance point.
6. EXPORT ALL LOADED AREAS saves the maps and pairings to disk.

The Entrance belongs to line shows exactly which exit owns the point.
SET ARRIVAL FOR SELECTED EXIT is a shortcut for the same placement action.
It is optional. Using or skipping it does not change the pairing.
ADD / UPDATE saves only the selected point. The incoming dropdown cannot
silently take over a point assigned to a different main exit.

WHAT THE TWO ENTRANCE FIELDS MEAN
- The point you place on the displayed map belongs to that map. It can be used
  as the return entrance beside the selected exit.
- Destination entrance (above) belongs to the destination map. It controls
  where the outgoing trip arrives. Choose an entrance in that destination.
- New exits use an existing destination entrance when available, avoiding
  nonexistent generated destinations that would prevent Export All.

OPTIONAL RETURN CONNECTION
After saving a point, choose an incoming exit and use LINK SELECTED ENTRANCE
TO INCOMING EXIT to make that incoming trip arrive at this point. Just choosing
the incoming row does not move, replace or link any point. The link action
refuses to take a route already assigned to another exit's saved point.

SAVING AND REOPENING
All entrance positions are written into the ARE file.
Exit/entrance pairings are also recorded in the existing AREA_TRANSITIONS.json
report (for example DR0002_TRANSITIONS.json). Keep this file beside the ARE,
especially if you rename an entrance. With the automatic entrance names, the
editor can recover the pairs from the ARE alone. A point missing its pairing
metadata is kept as an existing entrance; it is never deleted automatically.

Opening older ARE files keeps their existing entrances. The first point you
save for a newly paired exit gets a new independent name. START and older
arrivals stay in the list; only Delete selected entrance removes a point.

VALIDATION
RUN_ENTRANCE_TESTS.bat covers both the selected-exit workflow and the earlier
incoming-only workflow. Tests use actual PySide6 widgets and map clicks.
See V4_8_8_VALIDATION.json for the release results.
The supplied ARE files and chitin.key are not replaced by this package.
In-game execution is not tested here.

These notes supersede the earlier V4.8.7 entrance workflow notes.
